Fix storage account connection string configuration in Infrastructure as Code#69
Draft
Fix storage account connection string configuration in Infrastructure as Code#69
Conversation
Co-authored-by: mrsharm <68247673+mrsharm@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] [cpu-app] Storage account connection string not configured - runtime error and missing IaC configuration
Fix storage account connection string configuration in Infrastructure as Code
Jul 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes the runtime error in the
cpu-appwhere the/api/app/testendpoint was throwingInvalidOperationException: Storage account connection string is not configured.Problem
The application code was correctly looking for a storage account connection string via
app.GetConnectionString("StorageAccount"), but the infrastructure deployment (main.bicep) was not provisioning a storage account or configuring the connection string in the web app's settings.Solution
Updated the Bicep template to:
ConnectionStrings__StorageAccountwhich maps toConnectionStrings:StorageAccountin .NET Core configurationChanges Made
main.bicep: Added storage account resource and app setting configuration.gitignore: Addedmain.jsonto exclude generated ARM templatesTechnical Details
The connection string is dynamically generated using the storage account's name and primary key:
{ name: 'ConnectionStrings__StorageAccount' value: 'DefaultEndpointsProtocol=https;AccountName=${storageAccount.name};AccountKey=${storageAccount.listKeys().keys[0].value};EndpointSuffix=core.windows.net' }This resolves the runtime error while maintaining minimal changes to the existing codebase.
Fixes #68.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
aka.msbicep build main.bicep(dns block)bicep build main.bicep --stdout(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.